Method and system to verify data received, at a server system, for access and/or publication via the server system

ABSTRACT

A method and system to compare rendered publication data. The publication data are accessed from a database and then rendered to produce rendered publication data. The rendered publication data are stored to provide a reference version. After a periodic time interval, the publication data are accessed again and rendered to product a second version of rendered publication data. The reference version and the second version of rendered publication data are compared and a notification is generated when a difference exists.

This application claims the priority benefit of U.S. ProvisionalApplication No. 60/581,857 filed Jun. 21, 2004 and co-pending U.S.Utility application Ser. No. 10/875,443 filed Jun. 23, 2004, theapplications of which are incorporated herein by reference in theirentirety.

FIELD OF THE INVENTION

An embodiment relates generally to the technical field of electronicdata access and/or publication and, in one exemplary embodiment, to amethod and system to verify data received within an electroniccommunication at a server system.

BACKGROUND OF THE INVENTION

Electronic publishing, and the provision of access to content, has beenone of the driving forces behind the explosive growth of the Internet.Two examples of such electronic publishing, and data access, includeInternet-based commerce listings (e.g., classified advertisements,online auctions), which allow users to publish information regardingproducts and services for sale, and web-based e-mail (e.g., HOTMAIL™ andYAHOO! MAIL) that allow people to send electronic communications toother users.

In order to increase the richness of the presentation of informationaccessible, and communicated, via the Internet, a number of descriptorlanguages have emerged to support the authoring of content. The mostprominent of these are the so-called descriptor formats (e.g., HyperTextMarkup Language (HTML), eXtensible Markup Language (XML), etc.). Thesemarkup languages allow active content to be included within publishedcontent or communicated data to be rendered by a browser.

While active content has the potential to enrich the Internetexperience, it also presents a number of security problems andvulnerabilities. For example, unscrupulous and malicious users are ableto include malicious data (e.g., content) within active content of a webpage. Such malicious data may, for example, take the form of a virusthat infects the computer system of a user on which a web page isrendered or code that harvests private user information. The combatingof “malicious” data presents significant technical challenges to theoperators of web-based services. For example, a web-based e-mail serviceprovider may be challenged to exclude malicious data from e-mailcommunications. Similarly, the operator of a web-based commerce systemmay be challenged to ensure that listings, available from the commerceservice provider's web site, do not contain malicious data. Thetechnical challenges increase as the volume of communications processedby a particular web site increase.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example, and notlimitation, in the figures of the accompanying drawings, in which likereferences indicate similar elements, and which:

FIG. 1 is a block diagram illustrating the architecture of an activecontent system, according to an exemplary embodiment of the presentinvention.

FIG. 2 is a block diagram illustrating the architecture of an activecontent security system, according to a further embodiment of thepresent invention.

FIG. 3 is a block diagram illustrating a configuration console, whichmay be deployed in conjunction with, or as part of, an active contentsecurity system, according to an exemplary embodiment of the presentinvention.

FIG. 4 is a block diagram providing architectural detail regarding a webscrubber component of an active content security system, according to anexemplary embodiment of the present invention.

FIG. 5 is a block diagram illustrating a further exemplary embodiment ofan architecture of a web scrubber component that may be deployed as partof an active content security system.

FIG. 6 is a flowchart illustrating a method, according to an exemplaryembodiment, to verify active content to be published (or otherwise madeaccessible) by a computer system.

FIG. 7 is a flowchart illustrating a method, according to an exemplaryembodiment, to verify active content at a computer system.

FIGS. 8-9 are flowcharts illustrating a further exemplary method,according to one embodiment, to verify active content at a computersystem.

FIG. 10 is a network diagram depicting a commerce system, according toan exemplary embodiment, having a client-server architecture.

FIG. 11 is a block diagram illustrating multiple marketplace andpromotional applications that, in one exemplary embodiment, are providedas part of a network-based marketplace.

FIG. 12 is an entity-relationship diagram illustrating various tablesthat may be maintained within a database, according to one exemplaryembodiment, that supports a network-based marketplace.

FIG. 13 is a diagrammatic representation of a machine, in the exemplaryform of a computer system, within which a set of instructions forcausing the machine to perform any one of the methodologies discussedherein may be executed.

DETAILED DESCRIPTION

A method and system to verify publication data, received in data at acomputer system, are described. In the following description, forpurposes of explanation, numerous specific details are set forth inorder to provide a thorough understanding of the present invention. Itwill be evident, however, to one skilled in the art that the presentinvention may be practiced without these specific details.

One embodiment of the present invention is directed to the verificationof publication data (e.g., active content) to be published, or otherwisemade accessible, via a computer system. In one embodiment, the computersystem may operate as a server system in a client-server environment. Inother embodiments, the computer system may operate as a peer computerwithin a peer-to-peer architectured system.

An exemplary embodiment of the present invention is a discussed below asverifying “active content”. It will be appreciated that “active content”is merely one example of publication data that may be verified. For thepurpose of this specification, the term “active content” shall be takento include any data that may cause an action or activity to occur whenthe active content is accessed, received or processed. For example,active content may be data that includes executable code (e.g., ascript) that executes responsive to an onload event. Accordingly, activecontent may include a markup language document (e.g., HTML, XML, etc.),as a markup language document may cause a browser to be redirected to astorage location, and load or run applications. Active content may alsoinclude, for example, animated GIFs. Active content may also refer tomarkup language documents themselves (e.g., web pages that themselvesinclude, or contain references to, an executable script, such as, forexample, Java Applets, ActiveX controls, JavaScript, and Visual Basic).

Publication data (e.g., active content) may, for example, be mademalicious in two manners. Firstly, a malicious component of activecontent may be inserted directly into the active content (e.g., as anembedded script). Alternatively, a malicious component of active contentmay be distinct from data that includes the active content, but may belinked to data (e.g., by a URL that is included within the data). Inthis case, during a so-called “onload event,” a user browser may load aweb page, the browser then recognizing the link to the maliciouscomponent of the active content, and accordingly fetching the maliciouscomponent from a location identified by the URL.

One manner in which to avoid the security risks and problems presentedby active content is simply to prohibit active content from beingincluded in communications (e.g., e-mails or listings) received at acomputer system. However, this blanket approach is undesirable from anumber of points of view, not the least of which being that the richInternet experience that may be provided by active content is lost.

FIG. 1 is a block diagram illustrating an active content security system10, according to an exemplary embodiment, that may operate as acomponent of a computer system (e.g., a server computer system of awebsite), as a supplementary system to work alongside an existingcomputer system (e.g., a server system), or as a standalone system thatprovides security services, via a network, to other computer systems.The security system 10, in the exemplary embodiment, is shown to becoupled to one or more databases 12 that are written to via an interfacesystem 14, and from which information may be accessed or published via apublication/access system 16. Each of the interface andpublication/access systems 14 and 16 are coupled to a network 18 (e.g.,the Internet) so as to enable communications with other systems.

The active content security system 10, in one exemplary embodiment,includes a verification module 20 that includes a fetch process 22. Thefetch process 22 queries each of the databases 12 to extract activecontent therefrom. Consider the example in which the active contentsecurity system 10 is deployed in conjunction with a network-basedcommerce system. In this deployment, the interface system 14 may receivelistings, potentially including active content; these listings are thenstored within the databases 12. For example, the databases 12 may storelistings that are divided amongst the database components according tocategory. In this example, the fetch process 22 may query the databases12 to receive active content included in each of the listings within aparticular category or subcategory. The fetch process 22 mayperiodically cycle through each of the categories of listings stored inthe database 12. Of course, in other embodiments the resolution withwhich the fetch process 22 queries the databases 12 may be based on anyone or more criterion. The fetch process 22 may furthermore retrieve anentire communication, of which the active content forms merely a part,from the database, as well as other associated information to facilitateprocessing. Again, considering the example where a receivedcommunication is a listing, the fetch process 22 may retrieve the entirelisting, an item number allocated to the listing by a network-basedcommerce site, a time at which the listing was received, a useridentifier identifying the seller who added the listing, etc.

Having retrieved active content from the databases 12, the fetch process22 then caches the retrieved active content within a directory structure24. Storing the retrieved active within the directory structure 24enables the active content security system 10 to utilize the inherentabilities of a file system for locking, so as to coordinate and secureaccesses by different processes, within the security system 10 to theactive content. For example, the file locking capabilities of alow-level operating system may be utilized to ensure that processes donot overwrite each other.

The verification module 20 further includes a scan process 26, which inturn includes one or more filters that are applied to the activecontent, as stored within the directory structure 24. For example, thefilters may include heuristic filters 28, regular expression filters 30,Bayesian filters 32, as well as other custom filters 34. The variousfilters that constitute the scan process 26 are configured, on one hand,to perform simple scans to identify viruses and associated signatures,within the active content and, on the other hand, also to countersophisticated obfuscation techniques that may be employed to mask orhide malicious active content. Merely for example, malicious users mayinclude a URL in active content, which appears to point to harmlesscontent. However, the malicious user may associate a script with the URLthat, as an onload event, mutates the URL to cause a redirection tomalicious content. For example, the malicious user may exploit anembedded mathematical expression in a script that views the provided URLas variables, the script being able to concatenate these variablestogether in order to generate a new URL that points to maliciouscontent.

The verification module 20 is shown to provide output to a notificationmodule 36. In one embodiment, this output may constitute error codesthat are interpreted by the notification module 36 and processed togenerate one or more notifications. The notification module 36 includesa number of interfaces (e.g., an e-mail interface, a web interface, anSMS interface and a page interface), and is accordingly able to issuenotifications or alerts utilizing any one of a number of media andmechanism. Further, the modification module 36 may be programmed toprocess different errors in different ways. For example, where theverification module 20 detects a security threat that poses a high risk,the notifications or alerts issued by the notification module 36 may betailored accordingly. Further, the notification module 36 may include aknowledge management component (not shown) that, based on the type ofsecurity threat or error detected, may supplement informationcommunicated in a notification. For example, a notification may includecurrent information regarding a particular threat type, the currentinformation being retrieved from an external database that is updated byothers monitoring a particular threat.

The active content security system 10 also includes a web scrubber 40that, in one embodiment, operates to render active content (e.g., anHTML web page) so as to present the active content security system 10with a view of the active content as it will be rendered on anend-user's machine. This enables the active content security system 10to retrieve, analyze and verify content that is not directly included inreceived data (e.g., a communication), but is nonetheless accessed bythe active content as a result of a reference (e.g., a URL) includedwithin the received data. The web scrubber 40 accordingly includes arender engine 42 (e.g., the INTERNET EXPLORER or SAFARI render engines,developed by Microsoft Corporation and Apple Computer, Inc.,respectively). The web scrubber 40 further includes a web scanner 44that deploys one or more filters to detect malicious components ofactive content. In a further embodiment, the scan process 26 of theverification module 20 and the web scanner 44 may leverage a common setof filters in order to perform their respective functions.

The web scrubber 40, in a manner similar to the verification module 20,provides error codes to the notification module 36, so as to enable thegeneration and communication of suitable notifications and alerts.

In one embodiment, the notification module 36 may provide notificationsand alerts to a monitoring/server system 46 that, based on thenotification, may flag one or more data items (e.g., communications),which include active content, within the database 12 as being malicious.The monitoring/server system 46 may employ automated processes todetermine whether a particular data item, within the databases 12,should be flagged as being malicious based on an identified error orthreat. Further, the monitoring/server system 46 may include a manualreview process, where human operators review the error or the threatnotifications, before flagging a particular data item as malicious.

The publication/access system 16, in one embodiment, reviews flagsassociated with data items stored within the database in order to assesswhether to publish or otherwise provide access to a relevant data items.For example, in the exemplary embodiment where the databases 12 supporta network-based commerce system, a particular data item in the exemplaryform of a listing, which is flagged as being malicious, may be preventedfrom being accessible (e.g., either by search, browsing or otherwise)via the publication/access system 16.

FIG. 2 is a block diagram illustrating a further exemplary embodiment ofan active content, in which the verification module 20, of theembodiment illustrated in FIG. 1, is replaced by a fetch module 48 thatincludes a fetch process 50 and a mail forward process 52. The fetchprocess 50 operates in substantially the same manner as the fetchprocess 22 described above, to create a directory structure 24. The mailforward process 52 pulls active content (e.g., a listing) from thedirectory structure 24, and forwards the active content as an e-mailcommunication to a mail scrubber 54, which in turn includes a mailscanner 56. The mail scanner 56 may deploy a number of filters, such as,for example, anti-spam filters 58 and anti-virus filters 60. Thesefilters, in various embodiments, could again constitute heuristic,regular expression, Bayesian and other filter types. The mail scrubber54 then communicates any threats or errors detected by the mail scanner56 to the notification module 36.

The exemplary embodiment illustrated in FIG. 3 exhibits a more modulararchitecture than the exemplary embodiment illustrated in FIG. 1, andmay exhibit better scalability in certain environments. For example, themail scrubber 54 may be implemented utilizing an array of servers, withthe mail forward process 52 communicating e-mail messages, including theactive content, to the array of servers in a load-balanced manner.

FIG. 3 is a block diagram illustrating the architecture of a centralizedmanagement interface 70, according to an exemplary embodiment, that maybe utilized to upload different configurations to the various modulesand components of the active content security system 10. A centralmanagement interface (or console) 70 allows for the specification anduploading of different configurations for each of the major componentsof the active content security system 10 (e.g., the fetch module 48, themail scrubber 54, the web scrubber 40, and the notification module 36)to a configuration database 72. Local configuration files, maintained oneach of the components, are then synchronized with configuration filesmaintained within the database 72. The console 70 provides a centralplace for the modifying, changing, deleting and modifying ofconfiguration files for each of the components. The configuration filesmay, in one embodiment, specify the parameters and mechanisms to beemployed by the various filters of the mail scrubber 54 and the webscrubber 40, for example. A local configuration file for the fetchmodule 48 may furthermore specify the manner in which active content isto be retrieved from the databases 12, as well as a schedule for cyclingthrough the various databases 12. A local configuration file for thenotification module 36 may similarly specify the manner and timing ofthe issuance of notifications and alerts from the notification module36.

FIG. 4 is a block diagram providing further details regarding thearchitecture of the web scrubber 40, according to one exemplaryembodiment. FIG. 4 illustrates that the render engine 42 and the webscanner 44 (e.g., a web application firewall) may each reside on arespective proxy server. The render engine 42 is shown to receive activecontent (e.g., an HTML page), and to render this content. The renderingof the content may include the issuance of requests to external serversfor data (e.g., content, executable code, etc.) that resides on theseservers 74. Specifically, consider that active content in exemplary formof an HTML page may identify a location on an external server 74 fromwhich content is to be retrieved and displayed or executed within thecontext of the HTML document. During the rendering process, the renderengine 42, on encountering any data (e.g., content) on the HTML pagethat is externally referenced (e.g., by a URL), will issue a request forthe externally referenced data to the external server 74.

FIG. 4 illustrates that such a content request is routed to an externalserver 74 via the web scanner 44, resulting in the external servers 74returning the requested data via the web scanner 44 back to the renderengine 42. This provides the web scanner 44 with the opportunity toemploy filters 76 and error detection mechanisms 78 to verify that therequested data, as part of the rendered active content, is not malicious(e.g., is not a malicious executable code or script). The web scanner 44may or may not communicate the requested data to the render engine 42upon detection of malicious data, or on the verification that therequested data is in fact not malicious.

FIG. 5 is a block diagram illustrating a further exemplary embodiment ofcomponents that may be incorporated within the active content securitysystem 10. The embodiment illustrated in FIG. 5 differs from thatillustrated in FIG. 4, in that, in one embodiment, the render engine 42communicates all rendered data (e.g., rendered pages) to a cachingengine 90 that caches a “reference” copy of the rendered data for latercomparison, by a comparison engine 92, to a later rendered version ofthe rendered data. In an alternative embodiment, as opposed to cachingthe entire rendered data, the web scanner 44 may communicate linked datareceived from an external source (e.g., an external sever 74) to thecaching engine as a “reference” copy of linked data, which may becompared to a subsequently retrieved version of the linked data by thecomparison engine 92.

Referring to FIG. 5, a reference module, in the exemplary form of a linkmodule 80, is shown includes a reference parser, in the exemplary formof a link parser 82, that receives the active content from the renderengine 42, and parses all links (e.g., URLs) included in the activecontent to data that is linked to by the active content. The link parser80 then stores all identified links within a link archive 84 for laterdispatch, by a link dispatcher 86, back to the render engine 42. Thelink module 80 also includes a timer 88 whereby the timing of thedispatching of links from the link dispatcher 86 to the render engine 42is controlled.

In a further embodiment, the link parser 82 may form part of the webscrubber 40, and the web scrubber 40 may simply communicate links,identified within active content, to the link module 80 for archivingwithin the link archive 84.

In addition to simply archiving a record of the actual link, the linkarchive 84 also includes a time stamp indicating the date and timeinformation for when data (e.g., a communication, such as a listing) wasreceived at a specific system, as well as a time stamp indicating thetime and date at which the link dispatcher 86 last communicated therelevant link through to the render engine 42.

The link module 80 operates to maintain an archive of links, andassociated time/date information, so as to enable the active contentsecurity system 10 to repetitively and periodically verify that thedata, associated with the link and potentially stored at an externalserver location, has not been changed by a malicious user subsequent toan initial verification by the active content security system 10. Forexample, a malicious user, being aware that the active content securitysystem 10 will perform an initial verification with respect toexternally stored content referenced by active content received at asystem, may for an initial period associate benevolent data with thelink. After a predetermined time, having assumed that an initialverification by the active content security system 10 has beenperformed, the malicious user may then substitute the benevolent contentwith malicious content. The link module 80 operates in conjunction withthe web scrubber 40 to provide a continual monitoring of externalcontent that is referenced by active content published by a system(e.g., a network-based commerce system).

The link module 80 may accordingly, by issuing a link from a linkdispatcher 86 to the render engine 42, request and initiate averification process that utilizes the render engine 42 as a proxy forthe link module 80. The render engine 42 in turn utilizes the webscanner 44 as a proxy, the web scanner 44 requesting linked data (e.g.,linked content) from an external server 74 via the network 18. Thelinked content will then be returned to the web scanner 44 that employsthe filters 76 and error detection mechanisms 78 to scan the linkedcontent. The requested files (or appropriate error codes) are thenreturned from the web scanner 44 to the render engine 42.

In one embodiment, a rendered page, including the linked content, isthen provided to a further proxy server that hosts a caching engine 90,a comparison engine 92, and an alert engine 94. As noted above, in theembodiment illustrated in FIG. 5, the render engine 42 may deliverrendered pages content (e.g., rendered pages) to the caching engine forcached storage. The comparison engine 92 operates to compare apreviously stored version of rendered content with a newly receivedversion of the rendered content to determine whether the contentdiffers. Should the originally rendered version of the active contentdiffer from a subsequently rendered version of the active content, thisindicates that the content received from the external server, andassociated with a particular reference, may have been substituted formalicious purposes. Accordingly, the alert engine 94 may generate anappropriate indication to the notification module 36 in the event thecomparison detects such a variance.

In a further embodiment, the web scanner 44 may provide the retrievedlinked data directly to the proxy caching engine 90 which, as opposed tostoring an entire copy of rendered content, only stores the data that isretrieved from an external source (e.g., an external server 74). Thecomparison engine 92, it will be appreciated, may then perform acomparison between data previously received, and cached, from a locationidentified by a link with newly retrieved data from that location.Again, should the comparison engine 92 detect a delta between thepreviously archived content and the newly retrieved data, the alertengine 94 may issue an appropriate alert to the notification module 36.

FIG. 6 is a flowchart illustrating a method 100, according to anexemplary embodiment, to verify active content to be published oraccessed via a server system. At block 102, data is received at a serversystem (e.g., in the form of a listing received at a network-basedcommerce system or an e-mail received at a network-based email system),the received data including active content. The data may be received,for example, via the interface system 14 from a sending user (e.g., aseller that has offered a listing). The data is then stored, at block104, within the database 12, whereafter the fetch process 22, asdescribed above in reference to FIG. 1, retrieves a selected activecontent from the database 12. At block 108, the fetch process 22 storesthe retrieved active content in the directory structure 24. At block110, scanning processes (e.g., the scan process 26) of the verificationmodule 20 retrieve the active content from the directory structure 24,and apply one or more filters to the active content in an attempt toidentify malicious components thereof.

At decision block 112, the verification module 20 makes a determinationwhether any malicious content is identified as having been associatedwith the active content under consideration. If so, at block 114,appropriate error codes, which identify the nature of the maliciouscontent, are communicated to the notification module 36, which at block116, issues an appropriate notification/alert to the monitoring/serversystem 46. At block 118, the monitoring/server system 46 performs aconfirmation operation regarding the malicious content, and flags therelevant data, which included the malicious active content, in thedatabases 12. Accordingly, the flagging of the data identifies the dataas including malicious active content.

At block 120, the publication/access system 16 identifies the“malicious” flags associated with various data items in the databases12, and selectively publishes, or provides access, to data within thedatabases 12 based on the settings of the “malicious” flags. Forexample, where the databases 12 store data in the form of listings for anetwork-based commerce system, the publication/access system 16 may,responsive to a search request against the databases 12, exclude dataitems for which “malicious” flags have been set from a search resultreturn responsive to such a search query. Further, thepublication/access system 16 may simply prevent any processes of anetwork-based commerce system from exposing a data item that has beenflagged as being malicious.

Returning to decision block 112, in the event that the active contentunder scrutiny is not identified as having any malicious contentassociated therewith, the method 100 skips the operations performed atblocks 114-118, and accordingly a “malicious” flag is not set for therelevant content. At block 120, the publication/access system 116 mayallow access (or publication) of the data item associated with theactive content under scrutiny.

FIG. 7 is a flowchart illustrating a method 130, according to anexemplary embodiment, to verify active content at a server system (e.g.,a network-based commerce system). The method 130 commences at block 132,with the reception of received data (e.g., a listing or an email) via aninterface system 14, the received data including active content. Atblock 134, the render engine 42 retrieves the active content (e.g., fromthe directory structure 24) and initiates rendering thereof. At decisionblock 136, the render engine 42 makes a determination whether the activecontent includes a reference (e.g., a URL or other link) to an externalstorage location from which further data is to be retrieved.

If so, at block 138, the render engine 42 initiates a process toretrieve the data from the external storage location. To this end, therender engine 42 may issue a data request to the external server 74. Atblock 140, the render engine 42, as illustrated in FIG. 5, may alsocause the reference (e.g., the URL) to be stored in an archive (e.g.,the link archive 84), and may also cache the active content, and thedata retrieved from the external location, within the caching engine 90.It will be appreciated, from the above descriptions with reference toFIG. 5, that the caching of the active content, as well as the retrieveddata, within the caching engine 90 is for the purposes of creating a“reference” version of the active content and/or the retrieved data soas to enable the “reference” version to be compared against subsequentlyretrieved versions of this data, so as to enable detection of amodification to the external data associated with the reference.

In the event that the active content does not include a reference to anexternal storage location (decision block 136), or subsequently to thecaching operation performed at block 142, at block 144 the web scanner44 applies various filters and detection mechanism to the retrieveddata.

At decision block 146, the web scanner 44 makes a determination whethermalicious content was identified, by any other filters, as beingassociated with the active content (e.g., that the retrieved data itselfconstituted malicious active content). If so, at block 148, the webscanner 44 communicates appropriate error codes to the notificationmodule 36, which, in turn at block 150 provides a notification to themonitoring/server system 46. The monitoring/server system 46, at block152, may perform further scrutiny of the allegedly malicious content,and based on that scrutiny, flag the relevant data within the database12 as being malicious, if the scrutiny confirms the malicious nature ofthe content.

At block 154, the publication/access system 16 then reviews “malicious”flags associated with the data in the database 12, and selectivelypublishes, or provides access to, this data based on the settings of the“malicious” flags.

Similarly, at decision block 146, if it is determined that no maliciouscontent is associated with the active content under scrutiny, the method130 skips the operations performed at blocks 148-152, and progresses toblock 154. The method 130 then terminates at block 156.

FIGS. 8 and 9 are a flowchart illustrating a method 160, according to anexemplary embodiment, to verify content at a computer system (e.g. aserver system associated with a network-based commerce system). Themethod 160 commences at block 162 with the retrieval, by theverification module 20 of active content, and the passing, by the linkparser 82 of the active content to identify references (e.g., links inthe form of URLs) within the active content data external to datapreviously received by the interface system 14 and stored within thedatabases 12.

At block 164, the verification module 20, and more specifically, linkarchive 84, stores the identified references together with a receipttime stamp (e.g., indicating a date/time at which the data was receivedby the interface system 14), and a verification time stamp indicating atime at which the relevant reference was last verified. For an initialverification operation, the verification time stamp may be set to thedate/time at which the fetch process 22 retrieved the active contentfrom the databases 12.

It will be appreciated that the operations performed at block 162 and164 may correspond to the operations performed at block 140, asdescribed above with reference to FIG. 7. The operations are performedat blocks 166-198, as described below, [in our] reference specificallyoperations performed by the [no dictation].

At block 166, the link module 80 retrieves a next reference (e.g., URL)to be verified from the link archive 84, and at decision block 168determines whether a predetermined verification time interval haselapsed since the last verification time stamp. Specifically, the linkdispatcher 86 may compare the verification time stamp, associated withthe reference under scrutiny, with a current time in order to performthe determination at decision block 168.

Following a positive determination at decision block 168, the linkdispatcher 86 then sets the verification time stamp to the currentdate/time, and proceeds to dispatch the reference under scrutiny to therender engine 42, which acts as a proxy of the link module 80. Therender engine 42, in turn, issues a request for the retrieval of datafrom the relevant reference, this request being issued via the webscanner 44 to, for example, an external server 74 via the network 18.The external server 74 then returns the data, which resides at alocation identified by the reference to the web scanner 44. The webscanner 44 then communicates the retrieved data (e.g., the linkedcontent) to the caching engine 90 at block 174.

At decision block 176, the comparison engine 92 then performs acomparison between the retrieved data and a “reference” archived versionof the retrieved data to determine whether the newly retrieved datacorresponds to the “reference” archived version of the data.

In the event that the newly retrieved data is found not to correspond tothe “reference” archived version, at block 178, the alert engine 94issues an appropriate notification to the web scanner 44, which thenagain applies the appropriate filters and detection mechanisms to thenewly retrieved data to determine whether the newly retrieved, andmodified, data is malicious. In this manner, it will be appreciatedthat, by performing the comparison between the archived and newlyretrieved data, the scanning operations performed by the web scanner 44are only performed in the event that the data associated with aparticular reference is determined to have been modified subsequent to aprevious verification operation. The scanning operations, performed bythe web scanner 44, may be computationally expensive. By only performingthe scanning operations under these circumstances, the demand placed onthe web scanner 44 may be limited to those situations where dataassociated with a reference has in fact changed since a previouslyperformed verification operation with respect to the relevant reference.Accordingly, this allows the active content security system 10 toregularly and periodically verify data, without requiring that the webscanner 44 operate for each such regular and periodic verificationoperation.

Returning to the method 160, at block 180, in the event that maliciouscontent is identified as being associated with the active content (e.g.,the newly retrieved data is identified as being malicious), the method160 progresses to block 182, with the web scanner 44 providingappropriate error codes to the notification module 36. At block 184, thenotification module 36 provides appropriate notification to themonitoring/server system that, at block 186, in turn confirms themalicious nature of the newly retrieved data and may then set the“malicious” flag associated with the content in the database 12.

At block 188, as described above with reference to FIG. 7, thepublication/access system 16 may then examine “malicious” flagsassociated with data in the database 12, and selectively publish, orprovide access, to data based on the settings of relevant “malicious”flags. Subsequent to block 188, at block 198, the method 160 mayterminate.

Returning to FIG. 8, following a negative determination at decisionblock 168, or a positive determination at decision block 176, and,referring to FIG. 9, following operations performed at block 184, themethod 160 progresses to decision block 190, to perform a housekeepingfunction with respect to references in the link archive 84. In oneembodiment, at block 190, the link archive 84 may determine whether apredetermined lifetime interval has elapsed since the received timestamps associated with a particular reference. This determination is forhousekeeping purposes, and for removing references from the link archive84. In the exemplary embodiment in which the active content securitysystem 10 is operating in conjunction with a commerce system, thelifetime interval may be set to the maximum time period (e.g., 10 days)for which a commerce listing (e.g., an auction listing) may be valid.For example, where the time/date difference between the received timestamp and a current date/time, as specified by the timer 88, exceeds 10days, the method may progress to block 190, where the relevant referenceis removed following the operations performed at block 192, following anegative determination at decision block 190, the method againprogresses to block 198, where the method 160 terminates.

In an alternative embodiment, the housekeeping operation performed atblock 190 may use other criterion to remove a reference from the linkarchive 84. Where the active content security system 10 is deployed inconjunction with a commerce system, the link archive 84 may determinethat a listing, within which a particular reference is incorporated, isno longer valid or extant for a reason other than the expiration of alifetime. For example, the link archive 84 may determine whether an itemassociated with a listing has been sold, or where an auction listing hasexpired or has been otherwise terminated. A based on suchdeterminations, the link archive 84 may then remove a reference from thelink archive 84.

FIG. 10 is a network diagram depicting a commerce system 210, accordingto one exemplary embodiment, having a client-server architecture. Anexemplary active content security system 10 is shown to form part of thecommerce system 212. Specifically, a commerce platform, in the exemplaryform of a network-based marketplace 212, provides server-sidefunctionality, via a network 214 (e.g., the Internet) to one or moreclients. FIG. 10 illustrates, for example, a web client 216 (e.g., abrowser, such as the Internet Explorer browser developed by MicrosoftCorporation of Redmond, Wash. State), and a programmatic client 218executing on respective client machines 220 and 222.

Turning specifically to the network-based marketplace 212, anApplication Program Interface (API) server 224 and a web server 226 arecoupled to, and provide programmatic and web interfaces respectively to,one or more application servers 228. The application servers 228 hostone or more marketplace applications 230 and payment/redemptionapplications 232.

The application servers 228 are, in turn, shown to be coupled to one ormore databases servers 34 that facilitate access to one or moredatabases 236. The active content security system 10 is shown to becoupled to the databases 236, and accordingly, in one exemplaryembodiment, to operate in the manner described above with respect todata items contained within the databases 236.

The marketplace applications 230 provide a number of promotional,loyalty and marketplace functions and services to user that access themarketplace 212. The payment/redemption applications 232 likewiseprovide a number of payment and redemption services and functions toclients that access marketplace 212. Specifically, thepayment/redemption applications 230 allow users to quantify for, andaccumulate, value in accounts, and then later to redeem the accumulatedvalue for products (e.g., goods or services) that are made available viathe marketplace applications 230. While the marketplace andpayment/redemption applications 230 and 232 are shown in FIG. 10 to bothform part of the network-based marketplace 212, it will be appreciatedthat, in alternative embodiments, the payment/redemption applications232 may form part of a promotion or loyalty service that is separate anddistinct from the marketplace 212.

Further, while the system 210 shown in FIG. 10 employs a client-serverarchitecture, the present invention is of course not limited to such anarchitecture, and could equally well find application in a distributed,or peer-to-peer, architecture system. The various marketplace andpayment applications 230 and 232 could also be implemented as standalonesoftware programs, which do not necessarily have networkingcapabilities.

The web client 216, it will be appreciated, accesses the variousmarketplace and payment/redemption applications 230 and 232 via the webinterface supported by the web server 226. Similarly, the programmaticclient 218 accesses the various services and functions provided by themarketplace and payment/redemption applications 230 and 232 via theprogrammatic interface provided by the API server 224. The programmaticclient 218 may, for example, be a seller application (e.g., the TURBOLISTER application developed by eBay Inc., of San Jose, Calif.) toenable sellers to author and manage listings on the marketplace 212 inan off-line manner, and to perform batch-mode communications between theprogrammatic client 218 and the network-based marketplace 212.

FIG. 10 also illustrates a third party application 238, executing on athird party server machine 240, as having programmatic access to thenetwork-based marketplace 212 via the programmatic interface provided bythe API server 224. For example, the third party application 238 may,utilizing information retrieved from the network-based marketplace 212,support one or more features or functions on a website hosted by thethird party. The third party website may, for example, provide one ormore promotional, marketplace or payment/redemption functions that aresupported by the relevant applications of the network-based marketplace212.

FIG. 11 is a block diagram illustrating multiple marketplace andpromotional applications 230 that, in one exemplary embodiment, areprovided as part of the network-based marketplace 212. The marketplace212 may provide a number of listing and price-setting mechanisms wherebya seller can list goods or services for sale, a buyer can expressinterest in or indicate a desire to purchase such goods or services, anda price can be set for a transaction pertaining to the goods orservices. To this end, the marketplace applications 230 are shown toinclude one or more auction applications 244 with support auction-formatlistings and price setting mechanisms (e.g., English, Dutch, Vickrey,Chinese, Double, Reverse auctions etc.). The various auctionapplications 244 may also provide a number of features in support ofsuch auction-format listings, such as a reserve price feature whereby aseller may specify a reserve price in connection with a listing and aproxy-bidding feature whereby a bidder may invoke automated proxybidding.

A number of fixed-price applications 246 support fixed-price listingformats (e.g., the traditional classified advertisement-type listing ora catalogue listing) and buyout-type listings. Specifically, buyout-typelistings may be offered in conjunction with an auction-format listing,and allow a buyer to purchase goods or services, which are also beingoffered for sale via an auction, for a fixed-price which is typicallyhigher than the starting price of the auction.

Store applications 248 allow sellers to group their listings within a“virtual” store, which may be branded and otherwise personalized by andfor the sellers. Such a virtual store may also offer promotions,incentives and features that are specific and personalized to a relevantseller.

Reputation applications 250 allow parties that transact utilizing thenetwork-based marketplace 212 to establish, build and maintainreputations, which may be made available and published to potentialtrading partners. Specifically, where the network-based marketplace 212supports person-to-person trading, parties to a transaction may have nohistory or other reference information whereby trustworthiness andcredibility may be ascertained. The reputation applications 250 allow aparty, for example through feedback provided by other transactionpartners, to establish a reputation over time within the network-basedmarketplace 212. Other potential trading partners may then referencesuch a reputation for the purposes of assessing credibility andtrustworthiness.

Personalization applications 252 allow users of the marketplace 212 topersonalize various aspects of their interactions with the marketplace212. For example a user may, utilizing an appropriate personalizationapplication 252, create a personalized reference page at whichinformation regarding transactions to which the user has been a partymay be viewed. Further, a personalization application 252 may enable auser to personalize listings and other aspects of their interactionswith the marketplace 212 and other parties.

In one embodiment, the network-based marketplace 212 may support anumber of marketplaces that are customized, for example for specificgeographic regions. A version of the marketplace 212 may be customizedfor the United Kingdom, whereas another version of the marketplace 212may be customized for the United States. Each of these versions mayoperate as an independent marketplace, or may be customized (orinternationalized) presentations of a common underlying marketplace.

Navigation of the network based-marketplace 212 may be facilitated byone or more navigation applications 256. For example, a searchapplication enables key word searches of listings published via themarketplace 212. A browse application allows users to browse variouscategory, or catalogue, data structures according to which listings maybe classified within the marketplace 212. Various other navigationapplications may be provided to supplement the search and browsingapplications.

In order to make listings available via the network-based marketplace212 as visually informing and attractive as possible, the marketplaceapplications 230 may include one or more imaging applications 258utilizing which users may upload images for inclusion within listings.An imaging application 258 also operates to incorporate images withinviewed listings. The imaging applications 258 may also support one ormore promotional features, such as image galleries that may be presentedto potential buyers. For example, sellers may pay an additional fee tohave an image associated with one or more of the listings includedwithin a gallery of images for promoted items.

Listing creation applications 260 allow sellers conveniently to authorlistings pertaining to goods or services that they wish to transact viathe marketplace 212, and listing management applications 262 allowsellers to manage such listings. Specifically, where a particular sellerhas authored and/or published a large number of listings, the managementof such listings may present a challenge. The listing managementapplications 262 provide a number of features (e.g., auto-relisting,inventory level monitors, etc.) to assist the seller in managing suchlistings. One or more post-listing management applications 264 alsoassist sellers with a number of activities that typically occurpost-listing. For example, upon completion of an auction facilitated byone or more auction applications 244, a seller may wish to leavefeedback regarding a particular buyer. To this end, a post-listingmanagement application 264 may provide an interface to one or morereputation applications 250, so as to allow the seller conveniently toprovide feedback regarding multiple buyers to the reputationapplications 250.

Dispute resolution applications 266 provide mechanisms whereby disputesthat may arise between transacting parties may be resolved.Specifically, the dispute resolution applications 266 may provide guidedprocedures whereby the parties are guided through a number of steps inan attempt to settle the dispute. In the event that the dispute cannotbe settled via the guided procedures, the dispute may be escalated to athird party mediator or arbitrator.

A number of fraud prevention applications 268 implement various frauddetection and prevention mechanisms to reduce the occurrence of fraudwithin the marketplace 212. The fraud prevention applications 268 arealso shown to include, in one embodiment, an active content securityapplication, which may embody any one or more of the modules orcomponents described above. In this embodiment, the active contentsecurity system 10 may be tightly integrated into a network-basedmarketplace 212 as an application.

Messaging applications 278 are responsible for the generation anddelivery of messages to users of the network-based marketplace 212, suchmessages for example advising users regarding the status of listings atthe marketplace 212 (e.g., providing “outbid” notices to bidders duringan auction process or to provide promotional and merchandisinginformation to users).

Merchandising applications 280 support various merchandising functionsthat are made available to sellers to enable sellers to increase salesvia the marketplace 212. The merchandising applications 280 also operatethe various merchandising features that may be invoked by sellers, andmay monitor and track the success of merchandising strategies employedby sellers.

The network-based marketplace 212 itself, or one or more parties thattransact via the marketplace 212, may operate loyalty programs that aresupported by one or more loyalty/promotions applications 282. Forexample, a buyer may earn loyalty or promotions points for eachtransaction established and/or concluded with a particular seller viathe marketplace 212, and be offered a reward for which accumulatedloyalty points can be redeemed. A user may also accumulate value informs other than points. For example, value may be accumulated throughcoupons, gift certificates, etc.

The loyalty/promotion applications 282 include at least one accumulationmodule 284 that is responsible for registering the accumulation of value(e.g., points, coupons, gift certificates) within the accounts of users,and a redemption module 286 that is responsible for the redemption ofaccumulated value by users. Each of the accumulation and redemptionmodules 284 and 286 is shown to include a verification process, a lookupprocess, and an update process. The loyalty/promotion applications 282also include a statistics module 288 that, as will be described infurther detail below, is responsible for the generation of statisticspertaining to reward activities or events that may be registered withthe loyalty/promotion applications 282.

FIG. 12 is an entity-relationship diagram, illustrating various tables290 that may be maintained within the databases 236, and that areutilized by and support the marketplace 212 and payment/redemptionapplications 230 and 232. A user table 292 contains a record for eachregistered user of the network-based marketplace 212, and may includeidentifier, address and financial instrument information pertaining toeach such registered user. A user may, it will be appreciated, operateas a seller, a buyer, or both, within the network-based marketplace 212.In one exemplary embodiment of the present convention, a buyer may be auser that has accumulated value (e.g., promotional or loyalty points,coupons, gift certificates), and is then able to exchange theaccumulated value for items that are offered for sale by thenetwork-based marketplace 212.

The tables 290 also include an items table 294 in which is maintained anitem record for each item or service that is available to be, or hasbeen, transacted via the marketplace 212. Each item record within theitems table 294 may furthermore be linked to one or more user recordswithin the user table 292, so as to associate a seller and one or moreactual or potential buyers with each item record. In one exemplaryembodiment, certain of the items for which records exist within theitems table 294 may be promotional (or loyalty) items for whichpromotional or loyalty points (or other accumulated value) can beexchanged by a user. Any one or more of item records within the itemstable 294 may include active content, and accordingly be analyzed andverified by the active content security system 10, according to anexemplary embodiment.

A transaction table 296 contains a record for each transaction (e.g., apurchase transaction) pertaining to items for which records exist withinthe items table 294.

An order table 298 is populated with order records, each order recordbeing associated with an order. Each order, in turn, may be with respectto one or more transactions for which records exist within thetransactions table 296.

Bids records within a bids table 300 each relate to a bid receive at thenetwork-based marketplace 212 in connection with an auction form oflisting supported by an auction application 244. A feedback table 302 isutilized by one or more reputation applications 250, in one exemplaryembodiment, to construct and maintain reputation information concerningusers. A history table 304 maintains a history of transactions to whicha user has been a party. One or more attributes tables 306 recordattribute information pertaining to items for which records exist withinthe items table 294. Considering only a single example of such anattribute, the attributes tables 306 may indicate a currency attributeassociated with a particular item.

FIG. 13 shows a diagrammatic representation of machine in the exemplaryform of a computer system 400 within which a set of instructions, forcausing the machine to perform any one or more of the methodologiesdiscussed herein, may be executed. In various embodiments, the machineoperates as a standalone device or may be connected (e.g., networked) toother machines. In a networked deployment, the machine may operate inthe capacity of a server or a client machine in server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The machine may be a personal computer (PC), atablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), acellular telephone, a web appliance, a network router, switch or bridge,or any machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. Further,while only a single machine is illustrated, the term “machine” shallalso be taken to include any collection of machines that individually orjointly execute a set (or multiple sets) of instructions to perform anyone or more of the methodologies discussed herein.

The exemplary computer system 400 includes a processor 402 (e.g., acentral processing unit (CPU) a graphics processing unit (GPU) or both),a main memory 404 and a static memory 406, which communicate with eachother via a bus 408. The computer system 400 may further include a videodisplay unit 410 (e.g., a liquid crystal display (LCD) or a cathode raytube (CRT)). The computer system 400 also includes an alphanumeric inputdevice 412 (e.g., a keyboard), a cursor control device 414 (e.g., amouse), a disk drive unit 416, a signal generation device 418 (e.g., aspeaker) and a network interface device 420.

The disk drive unit 416 includes a machine-readable medium 422 on whichis stored one or more sets of instructions (e.g., software 424)embodying any one or more of the methodologies or functions describedherein. The software 424 may also reside, completely or at leastpartially, within the main memory 404 and/or within the processor 402during execution thereof by the computer system 400, the main memory 404and the processor 402 also constituting machine-readable media.

The software 424 may further be transmitted or received over a network426 via the network interface device 420.

While the machine-readable medium 422 is shown in an exemplaryembodiment to be a single medium, the term “machine-readable medium”should be taken to include a single medium or multiple media (e.g., acentralized or distributed database, and/or associated caches andservers) that store the one or more sets of instructions. The term“machine-readable medium” shall also be taken to include any medium thatis capable of storing, encoding or carrying a set of instructions forexecution by the machine and that cause the machine to perform any oneor more of the methodologies of the present invention. The term“machine-readable medium” shall accordingly be taken to included, butnot be limited to, solid-state memories, optical and magnetic media, andcarrier wave signals.

1. A publication system comprising: a processor; an electronic databasecoupled to the processor, the electronic database including publicationdata; a security system, coupled to the electronic database, to: accessthe publication data from the electronic database; render thepublication data to produce rendered publication data; store therendered publication data in an electronic storage cache to provide areference version of the rendered publication data; access thepublication data from the electronic database a second time after aperiodic time interval; render the publication data to produce a secondversion of rendered publication data; compare the second version ofrendered publication data to the reference version of the renderedpublication data; generate a notification when a difference existsbetween the second version of rendered publication data and thereference version of the rendered publication data store a flag, inresponse to the notification, the flag indicating that the publicationdata include allegedly malicious publication data; deny access to thepublication data when the flag indicating that the publication data isallegedly malicious is set; scan the publication data for maliciouscontent to obtain a scanning result; and clear the flag when thescanning result indicates that the publication data do not containmalicious content.
 2. The system of claim 1, wherein the publicationdata include a standardized descriptor language.
 3. The system of claim1, wherein to render the publication data to produce renderedpublication data, the security system is further configured to: parsethe publication data to identify externally referenced content; andissue a request for the externally referenced content.
 4. The system ofclaim 3, wherein the externally referenced content is configured to bestored at a server external to the publication system.
 5. The system ofclaim 1, wherein the notification provides an indication of a variancebetween the second version of rendered publication data and thereference version of the rendered publication data.
 6. The system ofclaim 1, wherein the security system is further configured to: publishthe publication data from the computerized publication system to aclient computer, in response to a request for the publication data fromthe client computer.
 7. A method of controlling access to publicationdata managed by a computerized publication system, the methodcomprising: accessing publication data from a database, the databasebeing associated with the computerized publication system and thepublication data including active content; rendering, on thecomputerized publication system, the publication data to producerendered publication data; storing the rendered publication data in anelectronic storage cache within the computerized publication system toprovide a reference version of the rendered publication data; accessingthe publication data from the database a second time after a periodictime interval; rendering, on the computerized publication system, thepublication data to produce a second version of rendered publicationdata; comparing, on the computerized publication system, the secondversion of rendered publication data to the reference version of therendered publication data; generating a notification when a differenceexists between the second version of rendered publication data and thereference version of the rendered publication data setting a flag, inresponse to the notification, the flag indicating that the publicationdata include allegedly malicious publication data; denying access to thepublication data when the flag indicating that the publication data isallegedly malicious is set; scanning the publication data for maliciouscontent to obtain a scanning result; and clearing the flag when thescanning result indicates that the publication data do not containmalicious content.
 8. The method of claim 7, wherein the publicationdata include a standardized descriptor language.
 9. The method of claim7, wherein rendering the publication data to produce renderedpublication data further comprises: parsing the publication data toidentify externally referenced content; and issuing a request for theexternally referenced content.
 10. The method of claim 9, wherein theexternally referenced content is stored at a server external to thecomputerized publication system.
 11. The method of claim 7, wherein thenotification provides an indication of a variance between the secondversion of rendered publication data and the reference version of therendered publication data.
 12. The method of claim 7, furthercomprising: publishing the publication data from the computerizedpublication system to a client computer, in response to a request forthe publication data from the client computer.
 13. A non-transitorycomputer-readable storage medium including instructions, which whenexecuted on a computerized publication system, cause the computerizedpublication system to: access publication data from a database, thedatabase being associated with the computerized publication system andthe publication data including active content; render the publicationdata to produce rendered publication data; store the renderedpublication data in an electronic storage cache to provide a referenceversion of the rendered publication data; access the publication datafrom the database a second time after a periodic time interval; renderthe publication data to produce a second version of rendered publicationdata; compare the second version of rendered publication data to thereference version of the rendered publication data; generate anotification when a difference exists between the second version ofrendered publication data and the reference version of the renderedpublication data store a flag, in response to the notification, the flagindicating that the publication data include allegedly maliciouspublication data; deny access to the publication data when the flagindicating that the publication data is allegedly malicious is set; scanthe publication data for malicious content to obtain a scanning result;and clear the flag when the scanning result indicates that thepublication data do not contain malicious content.
 14. Thenon-transitory computer-readable storage medium of claim 13, wherein thepublication data include a standardized descriptor language.
 15. Thenon-transitory computer-readable storage medium of claim 13, wherein theinstructions further include instructions that cause the computerizedpublication system to: parse the publication data to identify externallyreferenced content; and issue a request for the externally referencedcontent.
 16. The non-transitory computer-readable storage medium ofclaim 15, wherein the instructions to store the externally referencedcontent at a server external to the computerized publication system. 17.The non-transitory computer-readable storage medium of claim 13, whereinthe notification provides an indication of a variance between the secondversion of rendered publication data and the reference version of therendered publication data.
 18. The non-transitory computer-readablestorage medium of claim 13, wherein the instructions further includeinstruction which cause the computerized publication system to denyaccess to the publication data when the flag indicating that thepublication data is allegedly malicious is set.